🧪 Primary Scenarios Regression Suite
Environment: Develop
Schedule: Daily
Execution: GitHub Actions
Workflow: .on-demand - Primary Scenario Regression
✅ Test Coverage Overview​
| Spec File | Test Case Name | Functionality Touching | Application Touch Points |
|---|---|---|---|
| autoserve.should.not.allow.booking.enquiry.for.bot.user.spec.ts | Should not allow to procceed for Automation, BOT user | This file tests the Auto Serve web booking page blocks bots and works fine for real users across demo and prod environments. | Autoserve Web Booking |
| bookIn.enquiry.spec.ts | Should be able to create a new bookIn for a managed vehicle with Visn stock | This test validates that a book-in enquiry can be successfully created and submitted for a managed vehicle with Visn stock | V-Customer, V-Supplier |
| create.walkIn.enquiry.spec.ts | Should be able to create a new walk in enquiry for a managed vehicle | This test validates the complete Walk-In enquiry flow for a managed vehicle with Visn stock, covering system rule enabling, enquiry creation, job sheet preparation, authorisation, MOT submission, completion, invoice generation, and credit creation—ensuring everything works end-to-end. | V-Supplier, V-Customer |
| login.spec.ts | Should be able to login with valid lease credentials | This test verifies that a Lease user can successfully log in to the system | ViSN Login page |
| Should be able to login with valid supplier credentials | This test verifies that a Supplier user can successfully log in to the system | ViSN Login page | |
| Should not be able to login with invalid credentials | This test verifies login functionality with invalid credentials | ViSN Login page | |
| walkIn.enquiry.spec.ts | Should be able to create a new walk in enquiry for a managed vehicle and able to progress towards credit generation | This test covers the complete flow of creating, progressing, validating Request Authorisation button, invoicing, and crediting a Walk-In enquiry for a managed vehicle. | V-Supplier, V-Customer |
| walk.in.enquriy.without.driver.details.delete.vehicle.subcustomer.spec.ts | Create a new sub-customer and vehicle | This test verify sub-customer creation and vehicle creation | V-Customer |
| V-Supplier - Validate that the user can create a walk-in enquiry for a newly added vehicle by providing driver details on the walk-in screen | This test covers walk-in enquiry creation for a new vehicle with driver details, progresses the enquiry to completion, generates the invoice and credit, and validates both the uploaded PDF documents and related event logs. | V-Supplier, V-Customer | |
| V-Supplier - Validate that the user can create a walk-in enquiry for a newly added vehicle without providing driver details on the walk-in screen | This test includes walk-in enquiry creation for a newly added vehicle without driver details. | V-supplier | |
| V-Customer : Should be able to delete vehicle and Subcustomer | This test validate the deletion of vehicle and sub-customer | V-Customer | |
| glass.jobtype.spec.ts | Validate Glass Job Sheet component | This test covers end-to-end test validation of Glass Job Sheet component flow with ADAS calibration, amendments, and authorisation process | V-Supplier, V-Customer |
| login.spec.ts | Should be able to proceed after successful login | This test verifies that a Lease user can successfully log in to the system | V-Customer |
| customer.contract.import.validation.spec.ts | CustomerContract : Should be able to upload valid file and able to see validation status as success with success log | This test validates that a valid Customer Contract file can be uploaded successfully and shows a "Success" status with correct log details. | DI admin |
| CustomerContract : Should be able to upload invalid file and able to see validation status as failed with failure log | This test validates that an invalid Customer Contract file shows a "Failed" status with accurate error logs after upload. | DI admin | |
| legacy-import.validation.spec.ts | Legacy Stock : Should be able to upload valid file and able to see validation status as Success with success log | This test validates that a valid Legacy stock import file can be uploaded successfully and shows a "Success" status with correct log details. | |
| Legacy Stock : Should be able to upload invalid file and able to see validation status as Failed with failure log | This test validates that an invalid Legacy stock import file shows a "Failed" status with accurate error logs after upload. | ||
| amend.parts.fluid.delete.for.glass.spec.ts | Amend the Authrosiation requested enquiry from the customer and supplier end for glass job type | This test is used to amend and validate glass job line components from both lease and supplier site | V-Customer, V-Supplier |
| amend.parts.fluid.for.maintenance.spec.ts | Edit Parts and Fluid value from customer end | This test verifies the amendment of parts and fluid details from both lease and supplier sites and ensures the changes are reflected correctly on the supplier site for a maintenance repair job line. | V-Customer, V-Supplier |
| amend.parts.for.tyre.spec.ts | Amend the Authrosiation requested enquiry from the customer and supplier end for Tyre job type | This test verifies the amendment of tyre job line details from both lease and supplier sites and ensures the changes are reflected correctly on both site for a Tyre job line. | V-Customer, V-Supplier |
| authorisation.declined.service.history.spec.ts | Validate - Display Authorisation declined enquiries in the service history | This test verifies that declined authorisation enquiries appear in service history and are removed onced re-authorised | V-Customer, V-Supplier |
| no.agreed.rate.spec.ts | Should be able to see No agreed labour rate | This test verifies that the system displayes a warning when no agreed labour rates are in place during job sheet authorisation | V-Customer, V-Supplier |
| out.of.warrenty.vehicle.warrenty.rule.not.triggered.spec.ts | Should not generate warrenty warning for out of warrenty vehicle | This test use to validate that no warranty warning is triggered when progressing a job sheet for an out-of-warranty vehicle. | V-Customer, V-Supplier |
| refer.mot.rule.for.already.approved.but.on.hold.due.to.mot.status.fail.then.manual.send.spec.ts | Verify that the application places the enquiry on hold when the MOT rule triggers and allows the user to complete the enquiry with manual authorization, even if the MOT status is FAIL | This test verifies that an enquiry is placed on hold due to a FAIL MOT status, allows manual authorisation, and ensures the enquiry can proceed to completion, including invoice and credit generation | V-Customer, V-Supplier |
| refer.mot.rule.for.failed.mot.status.then.on.hold.should.removed.when.mot.status.to.pass.spec.ts | Verify that the application places the enquiry on hold when the MOT rule triggers and allows the user to complete the enquiry when the MOT status is marked as PASS | This test This test verifies that when an MOT fails, the enquiry is put on hold and only progresses after the MOT status is updated to PASS. | V-Customer, V-Supplier |
| system-rule-on-amend.jobsheet.from.suppplier.lease.validate.syetem.rule.trigger.spec.ts | Verify System rule gets triggers with job sheet amendment from supplier and lease side | This test validates that system rule warnings are correctly triggered when job sheet amendments are made from both the Supplier and Lease sides, covering the full enquiry progression from creation to invoicing and credit generation | V-Customer, V-Supplier |
| system-rule-on-amend.jobsheet.remove.job.item.from.partially.authorised.spec.ts | Should be able to perform amend operation with partially authorised and removed of rejected job items | This test verifies that a managed Visn stock vehicle enquiry can be amended after partial authorisation specifically by removing rejected job items resulting in auto-authorisation. It also validates MOT submission, ADAS certificate handling, and enquiry progression to completion | V-Customer, V-Supplier |
| system-rule-on-amend.parts.supplementry.spec.ts | Amend the Authrosiation requested enquiry from the customer and supplier side for Supplementry job type | This test validates the amendment flow for supplementary job types from both supplier and lease sides. It ensures changes, like updated part prices and reason codes, reflect correctly across users. | V-Customer, V-Supplier |
| system-rule-on-create.bookIn.enquiry.visn.managed.stock.till.credit.generate.spec.ts | Should be able to create a new bookIn for a managed vehicle with Visn stock and all syetem rules are in on state | This test covers end-to-end booking journey for a managed vehicle with Visn stock and all system rules enabled. It verifies authorisation, ADAS calibration, invoicing, and confirms all related documents are uploaded successfully | V-Customer, V-Supplier |
| authorisation.on.hold.new.update.spec.ts | Authorisation on Hold : New Update : Validate new update count getting increased and getting reset on view | This test validates that the "New Update" count increases correctly when a job sheet is amended for an enquiry in "Authorisation on Hold" status and reset count after viewing an enquiry | V-Customer,V-Supplier |
| book-in.validate.labour.rate.should.be.editable.when.labor.rate.coming.from.supplier.config.as.zero.spec.ts | Verify that the Labour Rate field is editable if its initial value is 0 or it has no value, also verify its not auto authorised | This test verifies that the Labour Rate field is editable when its initial value is 0 or blank in supplier config. It ensures both Supplier and Lease users can amend the labour rate and the updated value appears correctly in the invoice. | V-Customer, V-Supplier |
| maintenance.jobtype.spec.ts | Validate Maintenance Repair job component | This test covers the Maintenance Repair workflow, starting from walk-in enquiry creation to job sheet preparation, amendment, and re-authorisation. It validates inline error messages, amended cost updates, and entries in the maintenance history log | V-Customer, V-Supplier |
| Should be able to change the catalogue Job description to Non-catalogue | This test validates the behavior of Parts, Fluid, and Labour fields when changing a Maintenance Repair job description from catalogue to non-catalogue. | V-Customer, V-Supplier | |
| mot.jobtype.spec.ts | Validate MOT Job Sheet component | This test validates the MOT job line by checking inline messages, declining the enquiry, amending the job sheet to reduce the MOT cost, and verifying the updated values in the Job sheet historry drawer | V-Customer, V-Supplier |
| service.jobtype.spec.ts | Validate Service Job Sheet component | This test validates the service component inline messages, declining the enquiry, amending the job sheet to reduce the service cost, and verifying the updated values in the Job sheet historry drawer | V-Customer, V-Supplier |
| tyre.jobtype.spec.ts | Validate Tyre Job Sheet component | This test validates the tyre component inline messages, declining the enquiry, amending the reason code and verifu the amended details in Job sheet historry drawer | V-Customer, V-Supplier |
| role.whatsup.message.permission.spec.ts | Role > Whatsup > Enable/Disbale role and validate service access for VOR enquiry | This test verifies WhatsApp service access for VOR enquiries, based on whether the assigned role status is enabled or disabled. | V-Customer, V-Supplier |
| role.daily.agent.performance.spec.ts | VCustomer - Verify new permission 'Daily Agent Performance | This test validates role based access to the daily agent performance panel across Book-In, Authorisation and VOR modules.It verifies access is restricted or granted based on toggle settings in the user’s assigned role. | V-Customer, V-Supplier |
| role.monthly.platform.fee.repport.and.monthly.savi.report.permission.spec.ts | V-Customer > Roles > Validate Add/ View/Edit/Save a permission for 'Monthly SAVi Statement' and 'Monthly Platform fee' within 'Administration' permission on 'View Role' and Edit Role screen | This test verifies role-based access control for Monthly SAVi Statement and Monthly Platform Fee Report features in the Administration module, ensuring users can only view or interact with these based on assigned permissions | V-Customer, V-Supplier |
| role.settings.spec.ts | User should able to change toggle values and save it | This test verifies that user is able to enable and save expected roles | V-Customer |
| Disable parent service toggle and validate user not able to enable child service toggles | This test verify that user is not able to enable child service toggle if parent service toggle is disabled | V-Customer | |
| Enable Assign vor Ownership for user | This test vvalidate user having vor take ownership and release ownership access based on assigned role to the user | V-Customer | |
| Enable VOR toggle but disable Take ownership for user | This test verifies that the user cannot take or release ownership when the VOR toggle is enabled but the assigned role has the VOR Take Ownership and VOR Release Ownership permissions disabled. | V-Customer | |
| Disable View Job Sheet History for use | This test checks that the user is not able to access "Vehicle Checked In" and "Authorisation on Hold" statuses when the child role of VOR i.e "View Enquiry" role is disabled. | V-Customer | |
| Enable Control Panel setting, filters should be disabled | V-Customer | ||
| Disable Job sheet sheet history, validate Job Sheet history disabled in Service history drawer | This test checks that the user is not able to access Job Sheet History when the Job Sheet History toggle is disabled for their assigned role. | V-Customer | |
| VCustomer - Verify new role permission and user access for Archived Enquiries | This test checks that the user is not able to access Archived Enquiries when the Archived Enquiries toggle is dissabled for their assigned role | V-Customer | |
| license.check.with.valid.number.endate.on.convictiondate.spec.ts | Should be able to create a new sub-customer with license check enabled | This test is used to create new sub-customer with license check enabled | V-Customer |
| Should be able to create a new Driver with license check enabled | This test is used to create and validate new driver with license check enabled | V-Customer | |
| Should not be able to add valid driving license number on mandate complete screen and should be able to complete DVLA check | This test verifies that a valid UK driving license can be added to a drivers profile and the DVLA mandate check can be successfully completed. It also ensures penalty details are correctly retrieved and displayed after the DVLA check. | V-customer | |
| TC.2786.spec.ts | User should receive message when user provided optional services in invalid format | This API test validates that when a user submits a Book-In Enquiry with optional services in an invalid format, the system responds with appropriate error messages. It ensures validation for mandatory fields like current mileage, address code, and service type. | V-Customer |
| TC.2787.spec.ts | User should receive message when user provided optional services is not in uppercase format | This API test verifies that the system correctly returns an error when optional services are not provided in uppercase format in a Book-In Enquiry request. It also checks for mandatory field validations like current mileage, address code, and service type. | V-Customer |
| TC.2788.spec.ts | User should receive message when user provided optional services is not in valid format and provided optional services duplicate | This API test validates API responce for douplicate and invalid optional services along with missing mandatory fields in Book-In enquiry | V-Customer |
| TC.2789.spec.ts | User should receive message when user provided appointment date and time empty | This API test validates error handling when appointment date and time are missing during book-in enquiry creation. | V-Customer |
| TC.2790.spec.ts | User should receive message when user provided appointment date is not present | This API test verifies that the API returns appropriate errors when the appointment date is missing in the book-in enquiry request. | V-Customer |
| TC.2791.spec.ts | User should receive message when user provided appointment date is incorrect format | This API test is validates that the API returns an error when the appointment date is provided in an invalid format during enquiry creation. | V-Customer |
| TC.2792spec.ts | User should receive message when user provided appointment date is past dated | This API test ensures the API returns an error when a past appointment date is submitted during enquiry creation. | V-Customer |
| TC.2793.spec.ts | User should receive messages when user provided appointment time is not present | This API test validates that the API returns appropriate error messages when the appointment time is missing during enquiry creation. | V-Customer |
| TC.2794spec.ts | User should receive error message when user provided appointment time is not in correct present | This API test checks if the API correctly throws validation errors when the appointment time is in an invalid format | V-Customer |
| TC.2795.spec.ts | User should receive error message when the user-provided appointment time does not fall within the allowable working hours of the suppliers | This API test validates that the API returns an error when the appointment time falls outside supplier working hours (6:00 AM to 10:00 PM). | V-Customer |
| TC.2796.spec.ts | User should receive error message when the user-provided appointment dates exceed 10 dates | This API test validates that the API returns an error when more than 10 appointment dates are provided during enquiry creation. | V-Customer |
| TC.2797.spec.ts | User should receive error message when they provide invalid group ID and supplier ID | This API test is validates that the API returns appropriate errors when invalid groupId and supplierId are provided during enquiry creation | V-Customer |
| TC.2798spec.ts | User should receive error message when they provide an invalid group ID | This API test confirms that the API correctly flags an invalid groupId with appropriate error messages when creating a book-in enquiry | V-Customer |
| TC.2799.spec.ts | User should receive error message when they provide an invalid supplier ID | This API test validates that the API returns proper error messages when an invalid supplierId is provided in a book-in enquiry request | V-Customer |
| TC.2800.spec.ts | User should receive error message when the supplier ID and group ID they provide are not linked with the lease company | This API test validates that the API returns appropriate error messages when the provided groupId and supplierId are not linked to the selected lease company during book-in enquiry creation. | V-Customer |
| TC.2801.spec.ts | User should receive messages when user provided supplier id not matching with link lease company | This API test verifies that the system returns expected error messages when a supplier ID not linked to the selected lease company is used while creating a book-in enquiry | V-Customer |
| TC.2802.spec.ts | User should receive messages when user provided supplier is terminated | This API test checks that the API correctly returns validation error messages when a terminated supplier is used to create a book-in enquiry for a lease company | V-Customer |
| TC.2916.spec.ts | API : Book-In Enquiry : Create subcustomer , vehicle and progress enquiry towards credit generation | This E2E test automates the full Book-In Enquiry lifecycle, combining API and UI flows to create a sub-customer, vehicle, and progress the enquiry to invoicing. It validates key actions like submission, authorisation, MOT entry, and document upload across lease and supplier roles. | V-Customer-V-Supplier |
| TC.2832.spec.ts | User should receive a message when they provided VIN/VRM is empty | This API test validates error handling when creating a walk-in enquiry with missing VIN/VRM and other required fields. It reads input from a JSON file, sends a POST request, and asserts the API returns appropriate 400 error messages | V-Supplier |
| TC.2833.spec.ts | User should receive message when user does not provided VRM/VIN | This API test verifies that a proper 400 error response is returned when a walk-in enquiry is created without providing VIN or VRM. It uses structured test data and asserts all required error messages for missing vehicle and appointment details. | V-Supplier |
| TC.2834.spec.ts | User should receive message when user does not provide LeaseAPIId in request | This API test ensures a 400 error is returned when a walk-in enquiry request is submitted without the required leaseAPIId. It uses predefined test data and asserts the correct validation error message is received from the API. | V-Supplier |
| TC.2835.spec.ts | User should receive message when they provide invalid JobLine | This API test validates error handling when jobLines in a walk-in enquiry request is not in the expected format (array of objects). It ensures the API responds with a 400 status and the correct validation message. | V-Supplier |
| TC.2836.spec.ts | User should receive message when they provided jobLine is empty | This API test verifies the system's response when a walk-in enquiry request is sent with an empty jobLines array and missing key fields. It confirms that the API returns all expected validation error messages with status 400. | V-Supplier |
| TC.2837.spec.ts | User should receive message when user provide LeaseAPIId as an empty string in request | This API test checks that the system throws a validation error when the leaseAPIId is passed as an empty string. It ensures a proper 400 response with the error type LEASEAPIID_CANNOT_BE_EMPTY. | V-Supplier |
| TC.2838.spec.ts | User should receive message when user provided LeaseAPIId is not match with any entry in ViSN | This test case validates that the system responds with a 412 Precondition Failed when an invalid or unrecognized leaseAPIId is used. It confirms that the API returns the LEASEAPIID_NOT_FOUND error as expected. | V-Supplier |
| TC.2839.spec.ts | User should receive message when calling supplier does not have mapping with provided lease company | This test verifies that if a supplier is not mapped to the specified lease company, the API correctly responds with a 412 Precondition Failed error. | V-Supplier |
| TC.2841.spec.ts | Create a new Sub-customer | This test validates sub-customer creation flow by checking required field validations and successful form submission. Ensures the new sub-customer appears in the system and data is stored accurately | V-Customer |
| Create a new Vehicle | This test confirms vehicle creation process under a sub-customer by validating field checks and toast messages. Ensures the new vehicle is correctly saved and associated with the sub-customer | V-Customer | |
| User should receive response status as success when user provide only VIN in request | This API test sends an API request to create a walk-in enquiry using only the VIN field in the request body. It validates that the system responds with a 200 status and a success status message when the request is valid. | V-Customer, V-Supplier | |
| TC.2842.spec.ts | Create a new Sub-customer | This test validates sub-customer creation flow by checking required field validations and successful form submission. Ensures the new sub-customer appears in the system and data is stored accurately | V-Customer |
| Create a new Vehicle | This test confirms vehicle creation process under a sub-customer by validating field checks and toast messages. Ensures the new vehicle is correctly saved and associated with the sub-customer | V-Customer | |
| User should receive response status as success when user provide only VRM in request @endurance | This API test validate that a walk-in enquiry can be successfully created via API when only the VIN (Vehicle Identification Number) is provided in the request body. | V-Customer, V-supplier | |
| TC.2843.spec.ts | User should receive message when user not provide Mileage field in request | This API test validates that the API returns a 400 error when a walk-in enquiry request is made without mileage. Confirms the system correctly flags MILEAGE_IS_REQUIRED with an appropriate error message. | V-Supplier |
| TC.2844.spec.ts | User should receive message when user provide invalid Mileage | This API test checks if the API throws a 400 error for invalid mileage input during a walk-in enquiry. Validates the error type MILEAGE_IS_NOT_VALID and the corresponding message response. | V-Supplier |
| TC.2845.spec.ts | User should receive message when user not provide service type | This API test validates that a 400 error is returned when the serviceType field is not provided in the API request. Asserts that the response contains error type SERVICE_TYPE_CANNOT_BE_EMPTY with the correct message. | V-Supplier |
| TC.2846.spec.ts | User should receive message when user provided Service Type is not in Uppercase | This API test validates that a 400 error is returned when serviceType is in lowercase and other required fields are missing. Asserts that the response includes multiple error messages including SERVICE_TYPE_IS_NOT_VALID. | `V-Supplier |
| TC.2847.spec.ts | User should receive message when user provided Service Type is not present in Supplier configuration | This API teat checks if API returns a 400 error when the service type isn't configured for the supplier. Confirms that multiple validation errors are returned, including SERVICE_TYPE_IS_REQUIRED. | V-Supplier |
| TC.2849.spec.ts | User should receive message when user provide Invalid Driver name | This API test sends a request with an invalid driverName value. Expects multiple 400 validation errors, including DRIVER_NAME_IS_NOT_VALID. | V-Supplier |
| TC.2850.spec.ts | User should receive message when user provide Invalid Driver Email | This API test attempts to create a walk-in enquiry using an invalid driver email address. Verifies that the API returns a 400 response with DRIVER_EMAIL_IS_NOT_VALID and related validation errors. | V-Supplier |
| TC.2851.spec.ts | User should receive message when user provide Invalid Driver Contact | Validates that the API returns appropriate error messages when an invalid driver contact number is provided during Walk-In Enquiry creation. Ensures status code 400 with specific validation errors like missing jobLines, invalid contact, missing service type, and appointment object. | V-Supplier |
| TC.2852.spec.ts | User should receive message when user not provide Appointment Date and Time | This API test validates that the API returns appropriate errors when Appointment Date and Time are missing in a Walk-in enquiry request. | V-Supplier |
| TC.2853.spec.ts | User should receive message when user provide Invalid Appointment Date and Time | This test ensures the API returns appropriate errors for a Walk-in enquiry when the Appointment Date and Time are in an invalid format. | V-Supplier |
| TC.2854.spec.ts | User should receive message when user provide past Appointment Date | This API test validates that the API rejects Walk-in bookings with a past appointment date, returning the APPOINTMENT_DATE_CANNOT_BE_PAST_DATE error | V-Supplier |
| TC.2855.spec.ts | User should receive message when user provided Appointment Time is not within supplier working hours( 6.00 am to 22.00 pm) | This test verifies that the API rejects Walk-in bookings with appointment times outside supplier hours, returning the APPOINTMENT_TIME_NOT_WITHIN_SUPPLIERS_WORKING_HOURS error. | V-Supplier |
| TC.2856.spec.ts | User should receive message when user not provide JobLine type in Uppercase format | This API test ensures that the Walk-in booking API returns a JOBLINE_TYPE_IS_NOT_VALID error when the JobLine type is not in uppercase. | V-Supplier |
| TC.2857.spec.ts | User should receive message when user provide empty JobLine type in request | This API test validates that the Walk-in enquiry API returns a JOBLINE_TYPE_CANNOT_BE_EMPTY error when the job line type is left empty in the request. | V-Supplier |
| TC.2858.spec.ts | User should receive message when user not provide JobLine type | This API test verifies that the API returns appropriate validation errors when the JobLine type is missing in a walk-in enquiry request. | V-Supplier |
| TC.2859.spec.ts | User should receive message when user provided Location not in Uppercase format | This API test validates that the API responds with proper errors when Location is not in uppercase format in a walk-in enquiry request. | V-Supplier |
| TC.2860.spec.ts | User should receive message when user provide an empty Location | This API test ensures the API returns appropriate validation errors when the Location field is submitted empty in a walk-in enquiry request. | V-Supplier |
| TC.2861.spec.ts | User should receive message when user not provide Reason Code in request | This API test validates that the API returns appropriate errors when the Reason Code and other required fields are missing in the walk-in enquiry request. | V-Supplier |
| TC.2862.spec.ts | User should receive message when user provided Reason Code is empty | This API test ensures the API returns proper error messages when an empty Reason Code and other mandatory fields are submitted in a walk-in enquiry request. | V-Supplier |
| TC.2863.spec.ts | User should receive message when user provided Reason Code not specified (allowed numbers 1 to 40) | This API test validates that the API returns appropriate validation errors when the submitted Reason Code is outside the allowed range (1–40), along with missing mandatory fields in the walk-in enquiry request. | V-Supplier |
| TC.2864.spec.ts | User should receive message when user provided parts field is not in Array object format | This API test validates that the API returns an appropriate validation error when the parts field in the walk-in enquiry request is not submitted as an array of objects, as required by the API schema. | V-Supplier |
| TC.2865.spec.ts | User should receive message when user not provide Part Name | This API test ensures that the API correctly returns a validation error when the partName field is missing from the walk-in enquiry request payload, along with other dependent field validations. | V-Supplier |
| TC.2866.spec.ts | User should receive message when user provided Part Name is empty | This API test validates that the API returns appropriate error messages when the partName field is provided but left empty in a walk-in enquiry request, along with other required field validations. | V-Supplier |
| TC.2867.spec.ts | User should receive message when user provided Part Name is not in string format | This API test ensures the API correctly handles invalid input by returning appropriate error messages when the partName field is not a string, alongside validation for other required fields in the walk-in enquiry request. | V-Supplier |
| TC.2868.spec.ts | User should receive message when user not provide Part Number | This API test validates that the API returns the correct error messages when a partNumber is not provided in a walk-in enquiry request, along with enforcing other required fields like job description code and appointment details. | V-Supplier |
| TC.2869.spec.ts | User should receive message when user provide Invalid Part Number | This API test ensures that the API correctly responds with appropriate error messages when an invalid partNumber is submitted in a walk-in enquiry request, along with missing required fields such as job description code and appointment object. | V-Supplier |
| TC.2870.spec.ts | User should receive message when user not provide Part Quantity | This API test validates that the walk-in enquiry API returns appropriate error messages when the partQuantity field is missing from the request, along with other required fields such as jobDescriptionCode and appointment | V-Supplier |
| TC.2871.spec.ts | User should receive message when user provide Invalid Part Quantity | This API test ensures the walk-in enquiry API correctly returns validation errors when an invalid partQuantity value is provided in the request, alongside other missing required fields such as jobDescriptionCode and appointment. | V-Supplier |
| TC.2872.spec.ts | User should receive error message when user not provide Part Price | This API test validates that the walk-in enquiry API correctly returns appropriate validation error messages when the partPrice field is missing, along with required fields like jobDescriptionCode and appointment. | V-Supplier |
| TC.2873.spec.ts | User should receive error message when user provide Invalid Part Price | This API test verifies that the system returns appropriate validation error messages when an invalid partPrice value is provided in a walk-in enquiry API request. | V-Supplier |
| TC.2874.spec.ts | User should receive message when user not provide Part Manufacturer Goodwill % | This API test validates that the walk-in enquiry API returns an appropriate error when the Part Manufacturer Goodwill Percentage field is missing from the request payload. | V-Supplier |
| TC.2875.spec.ts | User should receive message when user provide Invalid Part Manufacturer Goodwill % | This API test verifies that the walk-in enquiry API correctly handles invalid values for Part Manufacturer Goodwill Percentage. | V-Supplier |
| TC.2876.spec.ts | User should receive message when user provide Invalid Labour Type | This API test validates the walk-in enquiry API response when an invalid format is used for the Labour field during enquiry creation. | V-Supplier |
| TC.2877.spec.ts | User should receive message when user not provide Labour Time | This API test validates that the API returns appropriate errors when Labour Time, Job Description Code, or Appointment fields are missing in a walk-in enquiry request. | V-Supplier |
| TC.2878.spec.ts | User should receive message when user provide Invalid Labour Time | This API test ensures the API returns proper validation errors when an invalid Labour Time is submitted in a walk-in enquiry request. | V-Supplier |
| TC.2879.spec.ts | User should receive message when user not provide Labour Manufacturer Goodwill % | This API test validates that the API returns appropriate errors when Labour Manufacturer Goodwill % is missing in a walk-in enquiry request. | V-Supplier |
| TC.2880.spec.ts | User should receive message when user provided Invalid Labour Manufacturer Goodwill % | This API test checks that the API correctly returns validation errors when an invalid Labour Manufacturer Goodwill % is submitted in a walk-in enquiry. | V-Supplier |
| TC.2881.spec.ts | User should receive message when user not provide Job Description Code | This API test verifies that the API returns an error when the Job Description Code is missing in the walk-in enquiry request. | V-Supplier |
| TC.2882.spec.ts | User should receive message when user provided Job Description code is empty | This API test validates that the API returns an error when the Job Description Code field is provided but left empty in the walk-in enquiry request. | V-Supplier |
| TC.2883.spec.ts | User should receive message when user provided Job Description code is not match to the available job description codes for the supplier | This API test ensures the API returns an error when the provided Job Description Code does not match any available job description codes for the selected supplier. | V-Supplier |
| TC.2884.spec.ts | API : Walk In Enquiry : Create a new Sub-customer, vehicle , enquiry and validate has open enquiry for already open enquiry | This API test validates the complete flow of creating a sub-customer and vehicle, submitting a walk-in enquiry via API, and ensuring the system returns an appropriate error when a duplicate enquiry is submitted for a vehicle that already has an open enquiry | V-Supplier |
| TC.2889.spec.ts | Create a new Sub-customer | This test validates sub-customer creation flow by checking required field validations and successful form submission. Ensures the new sub-customer appears in the system and data is stored accurately | V-Customer |
| Create a new Vehicle | This test confirms vehicle creation process under a sub-customer by validating field checks and toast messages. Ensures the new vehicle is correctly saved and associated with the sub-customer | V-Customer | |
| User should able to see API created Walk-In Enquiry on ViSN platform and able to take it towards credit generation | This API test verifies that a Walk-In Enquiry created via API is visible on the ViSN platform and can be progressed through all stages. It ensures end-to-end functionality from enquiry creation to credit generation, including invoice and document validation. | V-Customer,V-Supplier | |
| create.walkIn.enquiry.reassigned.to.another.supplier.spec.ts | Should be able to Re-assign Manual VOR enquiry to another suppliers | This test validates that a Manual VOR Walk-In enquiry with ViSN stock can be successfully reassigned to another supplier. It verifies the reassignment process and confirms the updated supplier assignment on the VOR screen. | V-Customer, V-Supplier |
| reassigned.to.another.visn.network.supplier.spec.ts | Should be able to Re-assign Book In enquiry to another supplier | This test ensures a Book-In enquiry with a ViSN stock vehicle can be created, submitted, accepted, and checked in, and then successfully reassigned to another supplier. It also confirms the reassignment is reflected correctly in the VOR search results | V-Customer, V-supplier |
| import.vehcile.create.bookIn.enquiry.till.credit.generate.spec.ts | Should be able to create a new bookIn for a managed imported vehicle with HP VRM look up check | This end-to-end test verifies the complete lifecycle of a Book-In enquiry for a managed imported vehicle with HP VRM lookup. | V-Customer, V-Supplier |
| hp.vrm.lookup.and.stock.addition.for.nonstockvehicles.spec.ts | Should be able to perform VRM Lookup and Addition of stock for non-stock vehicle by creating manual enquiry | This end-to-end test validates the full lifecycle of a manually created Book-In enquiry for a non-stock vehicle, ensuring that the vehicle is added to stock through the enquiry flow and its details are accurately reflected across the ViSN platform | V-Customer, V-Supplier |
| create.new.lease.company.setup.with.customer.network.spec.ts | |||
| - Should be able to create lease company for UK market with Customer Network as Rate card | This test validates that a UK-based lease company can be successfully created in DI Admin using the Customer Network as the selected rate card, and confirms proper form validations and submission. | Di admin | |
| - Should be able to create lease user, sub-customer, vehicle against newly created lease company | This test validates the end-to-end onboarding of a lease company user in DI Admin, including user invitation, registration, sub-customer creation, and successful vehicle addition for the newly created lease company. | Di admin | |
| - Should be able to create Group from DI Admin | This test validates the creation of a new DI Group in DI Admin, verifies its presence in the system, retrieves the group ID, and confirms the group's data is reflected in Looker reports (accounts_latest and accounts_changelog) | V-Customer | |
| - Should be able to update Group ID, Supplier Details in network import file | This test updates the network import CSV file by injecting the newly created Group ID, DI Group ID, Supplier Group Name, and Supplier Name to prepare it for importing into DI Admin. | Di admin | |
| - Should be able to import valid network import file against lease company | This test validates that a network import CSV file can be successfully uploaded and imported for a lease company in DI Admin, confirming the import initiation and success status. | Di admin | |
| - Should be able to create Supplier user against supplier from DI Admin | This test ensures that a supplier user can be successfully invited, receives the email, and completes new user registration via DI Admin. | Di admin | |
| - Should be able to see supplier details in looker report for tables > accounts_serviceUnit_latest and accounts_serviceUnit_changelog | This test verifies that supplier details from the network import file are accurately reflected in the accounts_serviceUnit_latest and accounts_serviceUnit_changelog Looker report tables. | Di admin | |
| - Should be able to see imported labor rates against the supplier | This test verifies that a lease user can view the imported labor rates against a supplier from the Supplier Details page. | V-Customer | |
| - Should be able to create book-in enquiry using newly created vehicle | This end-to-end test verifies the full Book-In Enquiry flow using a newly created vehicle, covering job creation, booking, acceptance, check-in, service pack validation, job sheet submission, authorisation, MOT details, enquiry progression, invoice generation, email receipt, invoice download, and credit note issuance. | V-Customer, V-Supplier | |
| system-rule-on-manual.auth.system.rule.off.auto.auth.spec.ts | Should not auto authorise for already manual authorised job line | This test verifies that a manually authorised MOT job line retains its status even after system rules are disabled. It also confirms that a new Service job line gets auto-authorised based on the updated system rule configuration. | V-Customer, V-Supplier |